Methods, systems and apparatuses for implementing time-triggered ethernet (tte) feature set scheduling with configuration-division multiplexing (cdm) to support in situ re-configuration and complex system commissioning

ABSTRACT

Methods, systems, and apparatuses for orchestrating the re-configuration of a Time-Triggered Ethernet (TTE) network for a plurality of configuration definitions (CDs) within a network configuration superset (NCS) by a Network Scheduling Tool (NST), including coupling a plurality of FSs to at least one common control FS (CCFS) to enable control by the NST of each FS by a runtime procedure wherein each FS of the plurality of FSs is composed of Virtual Links (VLs); scheduling the plurality of features sets (FSs) based on a target configuration of a specified FSs coupled to the CCFS within the TTE network; collecting, in a first scheduling pass by the NST, multiple FSs related to a plurality of phase configurations wherein the FSs are used to derive a specified target FS configuration; and forming a common FS by using an application to determine features associated with each FS of the plurality of FSs.

TECHNICAL FIELD

The present disclosure generally relates to methods, systems, andapparatuses for scheduling in time-triggered Ethernet (TTE) networks,and more particularly for specifying feature sets (FSs) and the use ofspecifications of one or more target TTE network configurationdefinitions (CDs) that include various combinations of the FSs for insitu system re-configuration and complex system commissioning.

BACKGROUND

Three basic approaches to system configuration include are-configuration based on a superset system, an orchestratedre-configuration, and a hybrid re-configurable system. The supersetapproach is the simplest approach wherein designers create a superset ofall known configurations, including all VL definitions and schedules, tolimit the amount of re-configuration required to execute a statetransition in the running system. Employing this method would likelyexhaust network resources, but could reduce CPU utilization in endsystems by employing intelligent input/output (I/O) control.

The implementation of orchestrated re-configuration can be considered acomplex approach to system configurability and can either beaccomplished in complete or incremental steps to the eventualre-configured system. The complete re-configuration approach may involvemultiple sets of matched network configurations, and those matchedconfiguration tables can either be resident in network hardware ordynamically loaded during system operation. No commonality is requiredbetween the multiple network configurations for completere-configuration to operate. For the complete re-configuration approach,all the network devices should receive a coordinated broadcast commandto update the active configuration table to the desired nextconfiguration followed by a reset command, if required by the hardwareimplementation. The entire system network, as a result, can beunavailable for an extended period, depending on hardware requirementsfor configuration table activation, before continuing with normaloperation in the new configuration.

Incremental re-configuration requires some amount of commonality amongthe different network configurations. Common sets of VLs are grouped,with at least one group common to all network configurations supportedin the re-configurable superset. The common control group is scheduledusing the exact trigger and arrival times in all network configurations.The same is true for all other VL groups as much as possible.Synchronization configuration remains the same in all networkconfigurations. This allows variation in the composition of VLs thatmake up a given complete network implementation while preserving as muchcommonality between them as possible. During the re-configurationprocess, specified upgrade zones would be moved to the newconfiguration. For example, one redundant plane of network switch cardswould transition to the new configuration, followed by a specific groupof end-system network interface cards. This process continues,incrementally, until the transition is complete. Since the commoncontrol group is scheduled identically in all network configurations,critical control of the vehicle is preserved throughout the transition.In this way, incremental re-configuration eliminates the systemunavailability typified by a complete re-configuration approach, butreductions in fault tolerance capabilities may be realized duringtransitions.

Moreover, the plans for future space vehicles include docking andconnecting multiple vehicles together with the sharing of command andcontrol responsibilities among the devices distributed throughout acomposed network in a process called complex system commissioning. Forlong-duration mission systems and vehicles, there is a need tore-configure the vehicle based on configuration changes that occur overtime in the mission and/or to prepare to connect with other newlydeveloped vehicles during the mission. Therefore, it is desirable toprovide a configuration-aware solution that distributes resourceallocation across different configuration domains with a runtimecapability of switching between configurations safely during vehicleoperation to support multiple use cases.

Hence, there is a need for methods, systems, and apparatuses for ahybrid approach to system re-configuration that combines feature set(FS) scheduling with the simplicity of the system supersetspecification. Other desirable features and characteristics will becomeapparent from the subsequent detailed description and the appendedclaims, taken in conjunction with the accompanying drawings and theforegoing technical field and background.

BRIEF SUMMARY

Methods, systems, and apparatuses are provided for scheduling aplurality of VLs in a TTE network.

In an exemplary embodiment, a method for orchestrating there-configuration of a Time-Triggered Ethernet (TTE) network by providingscheduling and configuration information for a plurality ofconfiguration definitions (CDs) within a network configuration superset(NCS) by a Network Scheduling Tool (NST), including: coupling aplurality of feature sets (FSs) to at least one CD within the NCS forthe TTE network enabling multiplexed configuration switching control bythe runtime system wherein each FS of the plurality of FSs is composedof at least one Virtual Link (VL) specification, metadata such asidentification information, and miscellaneous data such as inter-VLtiming and protocol information for the VL specifications in the FS,each CD is composed of at least one FS, metadata such as identificationinformation, and miscellaneous data such as modification information forVL specifications within a referenced FS, and the NCS is composed of atleast one CD, metadata such as identification information, andmiscellaneous data such as network-wide static configuration parameters;scheduling, by the NST, the VL specifications defined in a plurality offeatures sets (FSs) of the TTE network based on at least one target CDof specified FSs within the TTE network; collecting, in a firstscheduling pass by the NST, multiple FSs related to a plurality of CDswherein one or more of the FSs is referenced by more than one CD; andforming, by the NST, a common control feature set (CCFS) by using anapplication to determine the FSs common to all specified CDs in the NCS.

In various exemplary embodiments, the method including populating, bythe NST, a timeline divided into a generic global bin set designated asa baseline bin set for use in successive scheduling passes, wherein theglobal bin set is preserved by the NST for further processing of theplurality of FSs and populating of the timeline in successive passoperations. The method further including reconfiguring incrementally asspecified in at least one upgrade zone of an individual plane of the TTEnetwork wherein the NSCs operating on that plane transition from acurrent CD to a newly specified CD associated with different FSs. Themethod further including synchronizing, by the NST, by scheduling in asimilar manner using the CCFS other FSs resulting in configured sets ofVLs with a least amount of variations that compose the other FSs andpreserving at least some commonality between FSs in multiple target CDsin the NCS of the TTE network. The method further includingre-configuring, by the runtime system, using specified upgrade zonescomposed of select NSC planes each new table associated with acorresponding CD until in incremental transitions a final CDconfiguration transition is completed. The method further includingscheduling, by the NST, using the CCFS to preserve critical control ofphases of vehicle operation throughout each incremental transitionwherein any mutually exclusive FSs can be scheduled on top of existingscheduled FSs enabling VLs in each FS configuration to be configured inaccordance with one set of Network Interface Card (NIC) tables. Themethod further including producing, by the NST, a unique table for useby the NSC per target CD.

In another exemplary embodiment, a system for scheduling a plurality ofFeature Sets (FSs) in a Time-Triggered Ethernet (TTE) network using anetwork scheduling tool (NST), each of the plurality of VLs having ascheduled rate is provided. The system includes a plurality of FSscoupled to at least one CD in an NCS and a Network scheduling tool(NST), the NST configured to schedule a plurality of features sets (FSs)of the TTE network based on at least one target CD of specified FSswithin the TTE network; collect, in a first scheduling pass by the NST,multiple FSs related to a plurality of CDs wherein one or more of theFSs is referenced by more than one CD; and forming, by the NST, a commoncontrol feature set (CCFS) by using an application to determine the FSscommon to all specified CDs in the NCS.

In various exemplary embodiments, the system includes, the NST furtherconfigured to: populate a timeline associated with each FS using ageneric global bin set designated as a baseline bin set for use insuccessive scheduling passes, wherein the global bin set is preserved bythe NST for further processing of the plurality of FSs and populating ofthe timeline in successive pass operations.

The system includes the runtime system further configured tore-configure incrementally as specified in at least one upgrade zone ofan individual plane of the TTE network wherein the NSCs operating onthat plane transition from a current CD to a newly specified CDassociated with a different FSs. The system includes the NST furtherconfigured to: synchronize by scheduling in a similar manner using theCCFS other FSs resulting in configured sets of VLs with the least amountof variations that compose the other FSs and preserving at least somecommonality between FSs in multiple target CDs in the NCS of the TTEnetwork. The system includes the runtime system further configured tore-configure using specified upgrade zones composed of select NSC planeseach new table associated with a corresponding CD until in incrementaltransitions a final CD configuration transition is completed. The systemfurther includes the NST configured to schedule using the CCFS topreserve critical control of phases of vehicle operation throughout eachincremental transition wherein any mutually exclusive FSs can bescheduled on top of existing scheduled FSs enabling VLs in each FSconfiguration to be configured in accordance with one set of NetworkInterface Card (NIC) tables. The system further includes the NSTconfigured to: produce a unique table for use by the NSC per target CD.

In yet another exemplary embodiment, an apparatus including a NetworkScheduling Tool (NST) for scheduling a plurality of configurationdefinitions (CDs) within a network configuration superset (NCS) in aTime-Triggered Ethernet (TTE) network, is provided. The NST isconfigured with a processor programmed by a set of instructions toschedule time-triggered traffic wherein each CD in the NCS is coupled toa plurality of FSs within the TTE network enabling control by theprocessor of NST, the processor configured to schedule the VLspecifications defined in a plurality of features sets (FSs) of the TTEnetwork based on at least one target CD of specified FSs within the TTEnetwork; collect, in a first scheduling pass by the NST, multiple FSsrelated to a plurality of CDs wherein one or more of the FSs isreferenced by more than one CD; and form a common control feature set(CCFS) by using an application to determine the FSs common to allspecified CDs in the NCS.

In various exemplary embodiments, the NST further configured to:populate a timeline associated with each FS and VL specification using ageneric global bin set designated as a baseline bin set for use insuccessive scheduling passes, wherein the global bin set is preserved bythe NST for further processing of the plurality of FSs and populating ofthe timeline in successive pass operations.

The runtime system further configured to re-configure incrementallyusing specified upgrade zones composed of select NSC planes each newtable associated with a corresponding CD until in incrementaltransitions a final CD configuration transition is completed. The NSTfurther configured to: synchronize by scheduling in a similar mannerusing the CCFS other FSs resulting in configured sets of VLs with aleast amount of variations that compose the other FSs and preserving atleast some commonality between FSs in multiple target CDs in the NCS ofthe TTE network.

Furthermore, other desirable features and characteristics of the methodand system will become apparent from the subsequent detailed descriptionand the appended claims, taken in conjunction with the accompanyingdrawings and the preceding background.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention will hereinafter be described in conjunction withthe following figures, wherein like numerals denote like elements, andwherein:

FIG. 1 is a functional diagram of the layout of the time-triggeredEthernet (TTE) network with a network scheduling tool (NST) controlledby a feature set specification and tool input specification inaccordance with various embodiments.

FIG. 2 is a functional diagram of multiple different feature setsscheduled by the NST in accordance with various embodiments.

FIG. 3 is a functional diagram of a network configuration superset (NCS)of the TTE network in accordance with various embodiments.

FIG. 4 is a functional block diagram illustrating a time-triggeredEthernet (TTE) network with feature set data flows in accordance withexemplary embodiments;

FIG. 5 is a functional block diagram illustrating a TTE network withactive items in a common control feature set (CCFS) in accordance withexemplary embodiments;

FIG. 6 is a functional block diagram illustrating a TTE network withactive items in a common control feature set (CCFS) for an active launchphase in accordance with exemplary embodiments;

FIG. 7 is a functional block diagram illustrating a TTE network withactive items in a common control feature set (CCFS) for a docking phasein accordance with exemplary embodiments;

FIG. 8 is a functional block diagram illustrating a TTE network withactive items in a docking phase with reduced-rate CCFS in accordancewith exemplary embodiments;

FIG. 9 is a graph of a timeline of an exemplary CCFS schedule for aCDM-enabled TTE implementation in accordance with exemplary embodiments;

FIG. 10 is a graph of a timeline of an exemplary CCFS launch phaseschedule for a CDM-enabled TTE implementation in accordance withexemplary embodiments;

FIG. 11 is a graph of a timeline of an exemplary CCFS docking phaseschedule for a CDM-enabled TTE implementation in accordance withexemplary embodiments;

FIG. 12 is a graph of a timeline of an exemplary CCFS docking phaseschedule with CCFS rate reduction for a CDM-enabled TTE implementationin accordance with exemplary embodiments;

FIG. 13 is a flowchart for a rate reduction for a CDM-enabled TTEimplementation in accordance with exemplary embodiments; and

FIG. 14 is a block diagram of one embodiment of an exemplary NetworkScheduling Tool (NST) in accordance with exemplary embodiments.

DETAILED DESCRIPTION

The following detailed description is merely exemplary in nature and isnot intended to limit the disclosure or the application and uses of thedisclosure. As used herein, the word “exemplary” means “serving as anexample, instance, or illustration.” Thus, any embodiment describedherein as “exemplary” is not necessarily to be construed as preferred oradvantageous over other embodiments. All of the embodiments describedherein are exemplary embodiments provided to enable persons skilled inthe art to make or use the invention and not to limit the scope of theinvention, which is defined by the claims. Furthermore, there is nointention to be bound by any expressed or implied theory presented inthe preceding technical field, background, brief summary, or thefollowing detailed description.

Space vehicles include docking and connecting multiple vehicles togetherand sharing command and control responsibilities among the devicesdistributed throughout the composed network. For long-duration missionvehicles such as the Gateway, there is also an opportunity tore-configure the vehicle based on configuration changes over time or toprepare for connections to newly developed vehicles. There is a need toprovide a configuration-aware solution that distributes resourceallocation across different configuration domains with a runtimecapability of switching between configurations safely during vehicleoperation to support these use cases.

While the present disclosure describes methods and systems applicable tospace vehicles, it is contemplated the implementations of target featuresets, and configuration awareness solutions are equally applicable to avariety of different types of vehicles including but not limited toautomotive, aviation, and utility-type vehicles. Also, the configurationawareness solutions may, or can be implemented in fully autonomous,semi-autonomous, or driver-assisted vehicles.

Instead of implementing a superset approach, there is a need for asystem that utilizes configuration-division multiplexing (CDM) whileleveraging Network Switch Cards (NSCs) as bus guardians to provide anearly-seamless re-configuration process. There is a need that allmutually exclusive FSs can be scheduled on top of existing scheduled FSssuch that the VLs in these configurations will be based on one set ofnetwork interface card (NIC) tables. A unique configuration table foreach NSC is produced per target configuration definition, socurrent-generation TTE NSCs require a reset to transition to a newconfiguration. For long-term vehicle commissioning, combining the hybridapproach with incremental re-configuration allows greater changes to theVL sets. Since the hybrid network tooling is deterministic, FSs canlikely be combined in a variety of ways to make future vehicleintegration a seamless operation.

In various exemplary embodiments, the present disclosure describessystems, methods, and apparatuses for designing a spacecraft controlsystem with an innate awareness of varying system configurations thatlay the foundation for CDM. CDM allows the system to realize the runtimebenefits of dynamic input/output (I/O) configurations while retainingthe composable and verifiable nature of systems with static I/Odefinitions. In its most basic form, high-integrity modules control theactive configuration definition of the system and transition betweenconfiguration definitions, acting as the selector in the multiplexedenvironment. The superset of configuration definitions loaded into thesystem represent all designed combinations of supported I/Oconfigurations. Each configuration definition represents a whollyfunctioning and independently verifiable static I/O implementation for agiven vehicle configuration, mission phase, or any other unique statethat the system must support.

The implementation of CDM in some current TTE-capable hardware requiressome amount of commonality among the configuration definitions. Invarious exemplary embodiments of the present disclosure, the common setsof VLs are grouped into Feature Sets (FS), with at least one commoncontrol FS (CCFS) common to all configuration definitions supported inthe reconfigurable set. The CCFS is scheduled and configured identicallyin all configuration definitions. This allows variation in thecomposition of VLs that make up a given configuration definition whilepreserving as much commonality between them as possible. During there-configuration process, specified upgrade zones (i.e., one plane ofNSCs) move to the new configuration and continue until the transition iscomplete.

This present disclosure describes additional data flows to the networkscheduling tool suite to allow the specification of VLs grouped into FSsand the specification of one or more target configuration definitionsthat include various combinations of the FSs. More information must alsobe collected regarding the integrity level of target network nodes tosupport implementations relying on high-integrity NSCs as bus guardians.VL changes between configurations can include but are not limited toreducing the rate of specific VLs and the re-use of VL IDs for differentdata contents or different source or destination nodes in alternateconfiguration definitions.

Additionally, in alternate exemplary embodiments of the presentdisclosure, options are given to the tooling control in the data flowconfiguration and with behaviors to support the tooling. For example,this support may include incremental re-configuration that results in ahybrid reconfigurable system, with either NSC re-configuration requiredfor both high-integrity and standard-integrity Network Interface Card(NIC) state transitions, or NSC re-configuration required only forstandard-integrity NIC state transitions.

In various exemplary embodiments described in the present disclosure,the scheduling tool functionality may be augmented to perform thesorting and optimization of the grouped FSs into the specified targetconfiguration definitions. Multiple schedule passes can be performed onthe data sets. The first schedule pass can represent the collection ofFSs common to all target configuration definitions, and the result ofthat schedule pass would be used to populate a generic global bin set tobe used as a baseline for each successive schedule pass. The Bin setsresulting from all schedule passes would be preserved by the tooloutputs such that subsequent attempts to schedule additional VLs couldalso be attempted in the future. To support incrementalre-configuration, a unique set of formatted network outputs is producedafter each specified configuration definition is successfully scheduled.To support the hybrid reconfigurable system, tooling would post-processthe successfully scheduled network based on implemented HW constraintsto allow the overlapping valid VL definitions to coexist in the loadednetwork tables. HW constraints are unique to specific versions of targethardware but can include: for example, requirements such as N clocksseparating each scheduled VL transmit trigger value. The post-processinglogic in the tooling can, therefore, shift any conflicting VLs in timeto prevent that overlap and adjust corresponding NSC arrival timesaccordingly.

In various exemplary embodiments, the present disclosure describessupporting a configuration-aware upgrade to current TTE-enabled hardwaresince the current hardware generation does not contain any configurationinformation that specifies the assignment of VLs or other networkattributes to one or more target configuration definition. For example,configuration tables defining VL attributes in the TTE network hardwaremay be updated to contain a bit vector representing a one-hot encodedidentifier of valid configuration identifications to enable theapplication of a current table entry along with a global register thatrepresents a currently-operating configuration definition. In anexemplary example, in a system supporting 16 unique configurations, a16-bit vector would be required for each entry in each affected table,and a 4-bit value would be required for the global currently-operatingconfiguration register. Logic in the hardware devices would need to beupdated to mask and compare the valid configuration vector in tableentries to the currently-operating configuration register value todetermine if those table entries are valid for the currently-operatingconfiguration. Hence, this relatively small update to the hardwaredevices would allow the CDM approach to be supported natively inhardware and reduce the burden on software configuration requirements.

In various exemplary embodiments of the present disclosure, the softwareapplication implemented can produce data used by the Network SchedulingTool to perform network scheduling and configuration. The data residesinside the tool and its databases, and is transient and is destroyed andregenerated for each scheduling operation.

In various exemplary embodiments, the identical scheduling of the CCFSpreserves critical control of the vehicle throughout the transition. Theembodiments described below enable an improved network scheduling tool(NST) to more efficiently utilize the features and capabilities of theunderlying network hardware, such as to provide improved networkperformance with respect to such measures as latency, interference, etc.For example, the embodiments described below enable improved slot timeallocation and improved traffic management. Thus, when implemented bythe underlying hardware, the schedule and configuration parametersgenerated by embodiments of the NST described herein result in improvedperformance of the network. The various features of the NST describedherein can be used together or individually depending on the featuresand capabilities of the underlying network hardware.

In various exemplary embodiments, the present disclosure providesimproved enhancements to the NST for scheduling TTE networks. Theseapproaches have been shown to alleviate scheduling difficultiesencountered when scheduling data using the baseline implementation. Thisallows for a significant performance increase in the existing schedulerlogic by analyzing and utilizing additional information in the inputdata set to inform downstream scheduling decisions, providing systemdesigners additional input to control the behavior of the searchalgorithms, or by creating a dynamic scheduling algorithm based on novelapproaches in machine learning shown to be effective for optimizationproblems.

TT communication sends traffic based on globally synchronized time. TheTT packets are sent at predefined times and take priority over mostother traffic types in the network. The messages from higher layerprotocol can be made TT without modification to the messages themselves.The actual overhead from the protocol that enables TT traffic is sent inspecial messages. TTE protocol with TT communication is as a result onlyconcerned about when a message is sent not what specific content themessage has. The TT traffic is used for applications that require lowlatency, little jitter, and highly deterministic behavior.

The issued U.S. Pat. No. 9,762,501 B2 to Varadarajan et al. assigned toHONEYWELL® INTERNATIONAL INC., Morris Plain, N.J. (US) is incorporatedby reference and provides systems and methods for systematic hybridnetwork scheduling for multiple traffic classes with host timing andphase constraints using a method of scheduling communications in anetwork that includes scheduling transmission of VLs about a firsttraffic class on a global schedule. Also, to coordinate transmission ofthe Virtual Links about the first traffic class across all transmittingend stations on the global schedule.

The subject matter described here is related to the subject matterdescribed in the U.S. patent application Ser. No. 16/554,128 entitled“METHODS, SYSTEMS, AND APPARATUSES FOR OPTIMIZING TIME-TRIGGEREDETHERNET (TTE) NETWORK SCHEDULING BY BIN ALLOCATION, DEMAND PREDICTION,AND MACHINE LEARNING”, is incorporated by reference and describes theimplementation of a network scheduling tool (NST) for scheduling in TTEnetworks by determining a weight for each of the plurality of VLs, thedetermined weight being proportional to a demand each of the pluralityof VLs will place on the time-triggered ethernet network; generating aplurality of bins whose length in time is harmonic to all the scheduledrates of the plurality of VLs. Further, determining a demand valueproportional to how often the bin is expected to be used based upon agreen zone of each of the plurality of VLs and the determined weight foreach of the plurality of VLs, updating the demand value for each binwithin the green zone; sorting the plurality of bins from least demandedto most demanded based upon the updated demand value, and scheduling thesorted plurality of VLs within the sorted plurality of bins.

FIG. 1 is a functional diagram of the layout of the time-triggeredEthernet (TTE) network with a network scheduling tool (NST) controlledby a feature set specification and tool input specification inaccordance with various embodiments. In FIG. 1, the TTE network includesan NST 105, tool input specification 110, a network configurationsuperset metadata 155, feature set specification 125, configurationdefinition specification 135, device configuration files 115, and asystem reports and supporting files 140. In the TTE network, the toolinput specification 110 defines the configuration of the NST 105 forscheduling the feature sets with inputs from the configuration from thenetwork configuration superset metadata 155, the configurationdefinition specification 135, and the feature set specification 135. Theconfiguration definition specification 135 defines the differentconfiguration definitions (CDs) contained in the network configurationsuperset (NCS) with the network configuration superset metadata 155. TheNST 5 schedules the different feature sets (FSs) as defined in thefeature set specification 125 for different CDs within the NCS for theTTE network enabling multiplexed configuration switching control by aruntime system, The feature set specification 125 may define an FS witha Virtual Link (VL) specification, metadata such as identificationinformation, and miscellaneous data such as inter-VL timing and protocolinformation for the VL specifications in the FS. Each CD is composed ofa FS, of metadata such as identification information, and ofmiscellaneous data such as modification information for the VLspecifications within a referenced FS, and the NCS is composed of a CD,metadata such as identification information, and miscellaneous data suchas network-wide static configuration parameters.

The NST 5 schedules the VL specifications defined in different featuressets (FSs) of the TTE network by using a target CD of specified FSswithin the TTE network. The NST 5 may collect multiple FSs related todifferent CDs by using a common control feature set (CCFS) and using anapplication to determine the FSs common to all specified CDs in the NCS.The NST 5 can output device configuration files 115 and system reportsand supporting files 140 based on the schedule operations and definedspecifications of the different FSs.

FIG. 2 is a functional diagram of multiple different feature setsscheduled by the NST in accordance with various embodiments. In FIG. 2,feature set A (205), feature set B (210), and feature set C (215), areeach scheduled by the NST 5 (In FIG. 1). Each feature set (FS) is madeup of a set of virtual links (VLs) which are configured by a VLspecification 220. As an example, the feature set A (205) contains arespective set of FS metadata 230 and miscellaneous data 240 received bythe NST 5 for connecting the respective feature set to the NST 5 andother various modules and adapters in the flight phases.

FIG. 3 is a functional diagram of a network configuration superset (NCS)of the TTE network in accordance with various embodiments. In FIG. 3there is illustrated a network configuration superset (NCS) 300 which ismade up of two different combinations of features sets (FSs) that aredefined by the respective configuration definition (CD)-1 and CD-2. TheNCS 300 includes a set of NCS metadata 305 and miscellaneous data 315that are used in the scheduling of CD-1 and CD-2 and the respectivecombinations of FSs that make up CD-1 and CD-2. Each of the FS isconfigured as illustrated in FIG. 2. For Example, FS-A includes a VLspecification 220, FS metadata 230, and miscellaneous data 240 (See FIG.2). The NST (i.e. NST 105 of FIG. 1) schedules the different FSs (e.g.FS-A, FS-B, FS-C, and FS-D) as defined in the respective FSspecification for each of the different CD-1 and CD-2 within the NCS300.

FIG. 4 is a functional block diagram illustrating a time-triggeredEthernet (TTE) network with feature set data flows in accordance withexemplary embodiments. In FIG. 4 a simplified example TTE network 400 isdepicted with three feature sets identified. The common control featureset (CCFS) represents the virtual links (VLs) that remain identicallyscheduled throughout all configuration definitions.

In FIG. 4, the Time-Triggered Gigabit Ethernet (TTGbE) Network SwitchCard (NSC) 405 provides onboard communications between each of thesubsystems. TTGbE is a scalable highly deterministic full-duplexEthernet-compliant network that supports conflict-free command andcontrol using Time-Triggered (TT) traffic, video data using RateConstrained (RC) critical traffic and maintenance data using standardEthernet 802.3 Best Effort (BE) non-critical traffic on the samephysical interface. The TTGbE NSC 405 has 12-gigabit ports, handing 3traffic feature sets (the control set data, launch system data, and thedocking data), and is associated with one network plane. Fieldedfault-tolerant control systems include multiple network planes ofsimilarly-configured NSC devices.

FIG. 4 includes sensors and effectors 410, PDU controller 415, launchabort system 420, sensors and effectors 425, PDU controller 430, launchvehicle 435, docking adapter 440, NSC 405, and flight control module445. There is a common control feature set (CCFS) data 411 thatrepresents data flow between the sensors and effectors (410), thesensors and effectors (425), and the flight control module 445. The CCFSrepresents the VLs that remain identically scheduled throughout allconfiguration definitions. Two independent feature sets are defined forthe launch system data (412) and the docking data (413) and can containlaunch system and docking feature sets as mutually-exclusive sets ofVLs. The docking data for the docking feature set provides communicationbetween the flight control module 445 and the docking adapter 440. Thelaunch system data for the launch feature set provides communicationbetween the launch abort system 420 and the launch vehicle 435.

The TTE connection 421 connects the NSC 405 to each of the modules (i.e.the PDU controller 415, the PDU controller 430, the flight controlmodule 445, and the docking adapter 440) via the respective NetworkInterface Cards (NICs) 405-1, 405-2, 405-3, and 405-4. The backplanechannel 431 connects the PDU controller 430 to the launch vehicle 435and the sensors and effectors 425. Each of the NICs (405-1, 405-2,405-3, 405-4) and the NSC 405 represent the TTE network 400 equipmentforming the TTE network backbone. The backplane devices consist of thesensors and effectors 410, sensors and effectors 425, launch abortsystem 420, and the launch vehicle 435. The TTE network 400 isconfigured in a manner that assigns specific virtual links (VLs) andCommercial-Off-the-Shelf (COTS) data flows to independent feature sets,provides an integrity level of specific devices (i.e. the PDU controller430, the flight control module 445, the docking adapter 440, the PDUcontroller 415, etc.). The TTE network 400 is configured to enableidentical timing for feature sets common to multiple independentconfigurations, and using mutual exclusivity of feature sets to scheduleI/O events in an overlapping manner to effectively multiplex shared TTEnetwork resources. The NST tool schedules feature sets of the TTEnetwork 400 based on the target configuration definition of specifiedfeatures sets within the TTE network 400. The NST tool collects in afirst scheduling pass, multiple feature sets associated with the variousconfiguration definitions, and the feature sets collected are processedvia various applications to derive a specified target configurationdefinition. The target configuration definitions are specified as inputto the tool, and system designers group one or more VLs into eachfeature set, then one or more feature sets into a configurationdefinition. The plurality of configuration definitions includes thenetwork superset configuration.

Also, the NST can populate a timeline associated with each feature setand VL specification using a generic global bin set designated as abaseline bin set for use in successive scheduling passes. In this case,the global bin set is preserved by the NST for further processing of thefeature sets and populating of the timeline in successive passoperations. The NSC 405 re-configures incrementally in a defined upgradezone, one network plane at a time, by triggering a configuration tablereload, typically via a software-commanded reset operation, due tocurrent TTE hardware capabilities. The NST schedules the CCFS and otherfeature sets such that the global schedule contains a lesser amount ofvariation and allows the CCFS traffic to meet all schedule triggers andarrival checks in every target configuration definition specified forthe TTE network 400 superset configuration.

The NST schedule tool can operate to enable re-configuration usingspecified upgrade zones made up of selected NSC 405 network planes foreach new configuration definition which are changed in incrementaltransitions until the transition to the new configuration definition iscompleted. The NST may schedule using feature set commonality betweenconfiguration definitions, including, for example, the specification ofa CCFS, to preserve critical control of phases of vehicle operationthroughout each incremental transition. Also, any mutually exclusivefeature sets can be scheduled on top of an existing scheduled featureset. This can provide virtual links in each feature set configurationthat are formed as instructed in Network Interface Card (NIC) tables.The NST tool can produce a unique configuration table for use by the NSCper target configuration definition. Current generations of NSC 405hardware require a software-commanded reset to trigger each transition.FIGS. 5-8 are described with reference to the labeling in FIG. 4.

FIG. 5 is a functional block diagram illustrating a TTE network 400 withactive items in a common control feature set (CCFS) in accordance withexemplary embodiments. FIG. 5 depicts exemplary inputs for use byembodiments of the NST schedule tool and exemplary schedule andconfiguration parameters output by embodiments of the NST schedule tool.In FIG. 5, the common control set data (411) provides communicationbetween the NSC 405, the flight control module 445, the PDU controllers(415, 430), the sensors and effectors 410 and sensors and effectors 425.In FIG. 5, the TTE network 400 shows items active if the spacecraft isin a mission phase where only the CCFS is required. This entails thatthe flight control module 445 and both PDU controllers (415,430) receiveCCFS VL data via NIC (405-1, 405-2, 405-3) in an active mode to receiveand send CCFS VL data.

FIG. 6 is a functional block diagram illustrating a TTE network 400 ofanother configuration of feature sets of active items using a commoncontrol feature set (CCFS) and a launch system feature set in accordancewith exemplary embodiments. In FIG. 6, the launch system feature set 412and the CCFS 411 are active for items associated with a configurationdefinition for a launch phase. In this launch configuration, messagesare exchanged between the NSC 405, the flight control module 445, thePDU controllers (415, 430), the sensors and effectors 410 and sensorsand effectors 425 using the CCFS 411 and the launch system feature set.

FIG. 7 is a functional block diagram illustrating a TTE network 400 of aconfiguration definition of active items using a common control featureset (CCFS) and the docking data feature set in accordance with exemplaryembodiments. In FIG. 7, the docking data feature set 413 and the CCFS411 are active for items associated with a configuration definition fora docking phase. In this docking configuration, messages are exchangedusing the docking data feature set 413 between the NSC 405, the flightcontrol module 445, and the docking adapter 440.

FIG. 8 is a functional block diagram illustrating a TTE network 400 ofanother configuration definition of active items using a CCFS 411 andthe docking data feature set 413 in accordance with exemplaryembodiments. FIG. 8 illustrates another approach to specifying systemconfigurations to support a docking configuration different than theapproach of FIG. 7. In FIG. 8, the active items include a reduced set offunctionalities characterized by requiring the same set of VLs for thesame FSs but at lower rates 817 (reduced and de-rated data), the toolingcan allow the specification of rate reductions for individual VLs ineach of the active feature sets. Hence, in the docking phase, the CCFS411 is configured with specific VLs at lower harmonic transmit rates.

FIG. 9 illustrates a simplified global network timeline consisting of100 Hz, 50 Hz, and 25 Hz traffic reservations for the CCFS 411 (Of FIG.4) feature set in the example TTE network. Since all targetconfiguration definitions include the CCFS feature set, the toolingmaintains this schedule throughout subsequent scheduling activities. Inthe case of a fully CDM-enabled TTE implementation (i.e. TTE network400), there can be configured scheduling logic to generate completely ornearly completely independent schedules per target configuration.However, in such a case, if the functionality does not exist in thefielded hardware, then in implementation, maintaining separate scheduleinformation for TT traffic will likely require greater-sizedconfiguration tables than may be supported. Hence, to avoid this issue,the configuration for the tooling should or must define identical setsof scheduling information for each feature set across independentconfigurations in the TTE network.

This allows variable time allocations for I/O processing of networkscheduling and configuration tools and the intelligence (via intelligentapplications) to use configuration-specific timing for any trafficunique to that configuration definition. This allocation can be used todetermine worst-case I/O constraints for a particular VL found acrossall of the active configuration definitions enabled which provides fordifferent time allocations to application partitions that can bedependent on each mission phase or vehicle configuration.

The first schedule pass would represent the collection of feature setsthat are common to all target configuration definitions, and the resultof that schedule pass can be used to populate a generic global bin set.This generic global bin set in FIG. 9 is used as a baseline for eachsuccessive schedule pass. The bin sets resulting from all schedulepasses can be preserved by the NST outputs so subsequent attempts toschedule additional VLs may also be attempted in the future. To supportincremental re-configuration, a unique set of formatted network outputsis produced after each specified configuration definition issuccessfully scheduled. To support the hybrid reconfigurable system,tooling would post-process the successfully scheduled network based onthe implemented HW constraints to allow for the overlapping valid VLdefinitions to coexist in the loaded network tables. The HW constraintsare unique to specific versions of target hardware but can include, forexample, requirements such as N clocks separating each scheduled VLtransmit trigger value. The post-processing logic in the tooling would,therefore, shift any conflicting VLs in time to prevent overlap andadjust corresponding NSC arrival times accordingly.

FIG. 10 is a graph of a timeline of an exemplary launch phase schedulefor a CDM-enabled TTE implementation in accordance with exemplaryembodiments. FIG. 7 exemplifies this scheduling paradigm. The NSC toolschedules VL traffic for the launch-specific feature set in the gapsleft by the CCFS VLs. For this example, the NST treats the launch phaseand docking phase as independent configuration definitions.

FIG. 11 is a graph of a timeline of an exemplary docking phase schedulefor a CDM-enabled TTE implementation in accordance with exemplaryembodiments. This is an independent configuration definition thatsupports vehicle docking operations. The CCFS schedule slots remainidentical between the configurations. If the mission phase can include areduced set of functionalities which is characterized by requiring thesame set of VLs but at lower rates, the NST can allow the specificationof rate reductions for individual VLs in a feature set. The requirementsfor VL schedule commonality drive the need to retain identical triggerpoints in the global schedule, but the scheduling tooling can freealternating harmonic VL slots in the global schedule. Also, in the caseof different hardware which is implemented with native CDM support, theconfiguration tables can maintain unique references to differentschedules per required configuration definition. The current devicesrequire that end systems and switches preserve all the scheduled slotsfor these reduced-rate VLs, so when the feature set is designed, thefeature set should be limited to data sourced by high-integrity devices.

FIG. 12 is a graph of a timeline of an exemplary docking phase schedulewith CCFS rate reduction for a CDM-enabled TTE implementation inaccordance with exemplary embodiments. FIG. 12 illustrates CCFS trafficwith 100 Hz traffic reduced to 50 Hz. The patterned traffic reservationblocks represent the reduced-rate slots as well as the 50 Hz dockingtraffic that can now occupy those freed schedule areas. By reducing therates of VL traffic in alternate configuration definitions, the abilityof the scheduling tools is improved to converge on valid globalschedules, to limit resource utilization, and to potentially reducesystem sizes in high-traffic systems.

FIG. 13 is a flowchart for a rate reduction for a CDM-enabled TTEimplementation in accordance with exemplary embodiments. In FIG. 13 anexemplary flowchart 1300 of the multistep scheduling process ispresented. At task 1310, initially, the FSs commonality among the CDs isidentified. In an initial schedule pass executed by the NST forcollecting feature sets of all or nearly all of the target configurationdefinitions, the commonality between the respective FSs of each CD canbe identified. By including data flows to the network scheduling toolsuite, with the collected feature sets, the specification of VLs groupedinto FSs and the specification of one or more target configurationdefinitions that include various combinations of the FSs is enabled. Attask 1315, the CDs are sorted by complexity in descending order wherethe complexity is determined by examining the number of common FSs andthe total FS which are complementary in the CDs. After thisdetermination, at task 1320, which is after collecting the results fromthe initial schedule pass, a generic bin set is populated based on theresults, and the generic global bin set is established as a baseline foruse in successive scheduled passes.

At task 1325, each CD is scheduled by the NST. Next, after the initialschedule of the CD or CDs by the NST, the generic global bin set isupdated with all the common FS scheduling. At task 1345, it isdetermined if all the CDs have been cycled through and scheduled. Ifnot, then the flow reverts back to at task 1335, initializing a new CDbin set, and at task 1330 populating the new CD bin set with theapplicable FS reservations from the Global Bin Set, and applying atransformation such as VL rate reduction. At task 1330 for each VL in afeature, rate reductions are applied. Reducing the rates of VL trafficin alternate configurations can improve the ability of scheduling toolsto converge on valid global schedules, limit resource utilization, andpotentially reduce system sizing in high-traffic systems. Schedulingalgorithm updates would provide multiple scheduled configurationswherein feature sets common to multiple independent configurationdefinitions, CCFSs, maintain identical timing for scheduled I/Otriggers. The algorithm would overlap scheduled I/O triggers formutually exclusive feature sets. For any configurations that includecommon VLs but at different rates, the tooling would schedule the VLs atthe highest specified rate and then de-rate them by removing harmonicinstances of the VLs until the tool achieves the desired lower rate. Fora hybrid reconfiguration approach, the tooling would produce tables forend-system devices that include all VL triggers from all specifiedindependent configuration sets and multiple tables for eachhigh-integrity switching device-specific to an independent configurationdefinition.

The flow proceeds to again schedule the CD using the NST 1325 andsubsequently again updating the global bin set at task 1340 with all thecommon FS being scheduled.

Also, the bin set that is collected from all the scheduled passes ispreserved by the NST tool outputs to enable subsequent attempts toschedule additional VL's needed in future attempted executions. Thecollected information can or must also include the integrity level oftarget network nodes. By preserving the data, VL changes betweenconfigurations can include the re-use of VL IDs and reducing the rate ofa VL in an alternate configuration. The CCFS feature set is reserved andin this case for an exemplary timeline of time slots at 100 HZ, 50 HZ,and 25 HZ.

Alternatively, if all the CDs are scheduled at task 1345, then at task1350 the CDs are merged into the Network configuration superset. At task1355, the technology-specific hardware constraints to overlapping VLdefinitions are applied. Hence, the tooling post-processing is executedbased on the implemented hardware configurations used in each phase ofthe spacecraft. In this case there about 14 different phaseconfigurations for each flight phase. This allows the overlapping ofvalid VL definitions to coexist in loaded network tables for eachhardware configuration. The hardware constraints are unique to eachconfiguration, and specific to each version of targeted hardware but canbe modified with system requirements such as N clocks separating eachscheduled VL transmit trigger value. Then, at task 1360, the deviceconfiguration tables based on the HW constraints are produced and inputsof the re-configuration specification are performed.

Also, to support incremental re-configuration, a unique set of formattednetwork outputs is produced after each specified configurationdefinition is successfully scheduled. The VL traffic is scheduled forspecific configuration definitions (i.e. for launch, docking, etc.), andCCFS scheduled time slots that are identical are identified across thespecific configurations. This can support a hybrid reconfigurable systemwhere the tooling would post-process a scheduled network based onimplemented hardware constraints and allow the overlapping of valid VLdefinitions to coexist in the loaded network tables.

Currently, the TTE-enabled hardware does not contain any configurationinformation that can uniquely identify any table entries specific to VLsas being part of a given FS or target configuration definition. Thisinvention can also support a configuration-aware upgrade to currentTTE-enabled hardware wherein configuration tables defining VL attributesin the TTE network hardware contain a bit vector representing a one-hotencoded identifier of valid configuration identifications to which thecurrent table entry applies along with a global register that representsthe currently-operating configuration. For example, in a systemsupporting 16 unique configurations, a 16-bit vector would be requiredfor each entry in each affected table, and a 4-bit value would berequired for the global currently-operating configuration register.Logic in the HW devices would need to be updated to mask and compare thevalid configuration vector in table entries to the currently-operatingconfiguration register value to determine if those table entries arevalid for the currently-operating configuration. This is a relativelysmall update to the hardware devices that would allow the CDM approachto be supported natively in hardware and reduce the burden on softwareconfiguration requirements.

Tooling will need to support any hardware-specific requirements andconstraints such as schedule trigger separation requirements and performany timing adjustments required to accommodate the current-generationhardware. At task 1355, the post-processing logic in the tooling would,therefore, shift any conflicting VLs in time to prevent that overlap andadjust corresponding NSC arrival times accordingly.

FIG. 14 is a block diagram of one embodiment of an exemplary NetworkScheduling Tool (NST) in accordance with various embodiments. The TTEnetwork 100 (of FIG. 1) with the NST 1400 can be implemented usingsuitable hardware and protocols which can be configured to support oneor more of the functions described herein. For example, for purposes ofexplanation, the embodiments described herein are implemented using theTTE protocol and compatible hardware as defined in the SAE AS6802standard. However, it is to be understood that other hardware andprotocols can be used in other embodiments. For example, other exemplarynetwork implementations include, but are not limited to, ethernet-basednetworks including Avionics Full-Duplex Switched (AFDX) Ethernet definedin the ARINC 664 Part 7 standard and non-Ethernet based store andforward networks. The NST 1400 includes a Network Scheduling Tool (NST)1410 used to schedule transmission of messages (also referred to hereinas frames) through the TTE network as well as determine otherconfiguration parameters for operation of the TTE network.

The NST 1410 provides configuration data for onboard communicationsbetween each of the subsystems. inputs for use by embodiments of the NST1410 and exemplary schedule and configuration parameters output byembodiments of the NST 1410. In particular, the exemplary inputs includeVL inputs, global system inputs, and localhost inputs. The VL inputs foreach VL can include the VL identification number, the source networkinterface card (NIC), the set of reception nodes, routing information,payload size, traffic class, transmit rate, and schedule type of a fastpass or a normal pass scheduling.

FIG. 14 illustrates an NST 1410 with a processing unit, memory, andinterface of an exemplary NST in accordance with an embodiment. The NST1410 includes an input/output interface 1402, a processing unit 1404,and a memory 1406. Network scheduling instructions 1408 are stored inthe memory 1406. The processing unit 1404 includes or functions withsoftware programs, firmware or other computer-readable instructions(e.g., network scheduling instructions 1408) for carrying out variousmethods, process tasks, calculations, and control functions, used inperforming the functions described herein, such as scheduling featuresets of the TTE network based on the target configuration of specifiedfeatures sets connected to the control channel within the TTE network;for populating a timeline associated with each feature set and VLspecification using a generic global bin set designated as a baselinebin set for use in successive scheduling passes, and for reconfiguringincrementally using specified upgrade zones composed of select NSC. Forexample, this may include a described transition from a current CD to anewly specified CD associated with different FSs. The NST 1400 and NST1410 can synchronize the schedule using the CCFS other FSs resulting inconfigured sets of VLs with a least amount of variations that composethe other FSs and preserving at least some commonality between FSs inmultiple target CDs in the NCS of the TTE network.

These instructions are typically stored on any appropriatecomputer-readable medium used for storage of computer-readableinstructions or data structures. The computer-readable medium can beimplemented as any available media that can be accessed by ageneral-purpose or special-purpose computer or processor, or anyprogrammable logic device. Suitable processor-readable media may includestorage or memory media such as magnetic or optical media.

By executing the network scheduling instructions 1408, the processingunit 1404 computes network configuration and scheduling tables which areoutput via the input/output interface 1402. The network schedulinginstructions 1408 are configured to cause the processing unit 1404 toimplement some or all of the techniques described herein to compute theconfiguration and schedule tables. The configuration and schedule tablescan be loaded into the various nodes (e.g., end systems and switches) ofthe network for managing the frames that flow through the network.Hence, the NST 1410 need not be implemented as a node in the network.

Those of skill in the art will appreciate that the various illustrativelogical blocks, modules, and algorithm steps described in connectionwith the embodiments disclosed herein may be implemented as electronichardware, computer software, or combinations of both. Some of theembodiments and implementations are described above in terms offunctional and/or logical block components (or modules) and variousprocessing steps. However, it should be appreciated that such blockcomponents (or modules) may be realized by any number of hardware,software, and/or firmware components configured to perform the specifiedfunctions. To clearly illustrate this interchangeability of hardware andsoftware, various illustrative components, blocks, modules, circuits,and steps have been described above generally in terms of theirfunctionality.

Whether such functionality is implemented as hardware or softwaredepends upon the particular application and design constraints imposedon the overall system. Skilled artisans may implement the describedfunctionality in varying ways for each particular application, but suchimplementation decisions should not be interpreted as causing adeparture from the scope of the present invention. For example, anembodiment of a system or a component may employ various integratedcircuit components, e.g., memory elements, digital signal processingelements, logic elements, look-up tables, or the like, which may carryout a variety of functions under the control of one or moremicroprocessors or other control devices. Also, those skilled in the artwill appreciate that the embodiments described herein are merelyexemplary implementations

The various illustrative logical blocks, modules, and circuits describedin connection with the embodiments disclosed herein may be implementedor performed with a general-purpose processor, a digital signalprocessor (DSP), an application-specific integrated circuit (ASIC), afield-programmable gate array (FPGA) or another programmable logicdevice, discrete gate or transistor logic, discrete hardware components,or any combination thereof designed to perform the functions describedherein. A general-purpose processor may be a microprocessor, but in thealternative, the processor may be any conventional processor,controller, microcontroller, or state machine. A processor may also beimplemented as a combination of computing devices, e.g., a combinationof a DSP and a microprocessor, a plurality of microprocessors, one ormore microprocessors in conjunction with a DSP core, or any other suchconfiguration.

The steps of a method or algorithm described in connection with theembodiments disclosed herein may be embodied directly in hardware, in asoftware module executed by a processor, or in a combination of the two.A software module may reside in RAM, flash memory, ROM memory, EPROMmemory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM,or any other form of storage medium known in the art. An exemplarystorage medium is coupled to the processor such the processor can readinformation from, and write information to, the storage medium. In thealternative, the storage medium may be integral to the processor. Theprocessor and the storage medium may reside in an ASIC. The ASIC mayreside in a user terminal. In the alternative, the processor and thestorage medium may reside as discrete components in a user terminal.

In this document, relational terms such as first and second, and thelike may be used solely to distinguish one entity or action from anotherentity or action without necessarily requiring or implying any actualsuch relationship or order between such entities or actions. Numericalordinals such as “first,” “second,” “third,” etc. simply denotedifferent singles of a plurality and do not imply any order or sequenceunless specifically defined by the claim language. The sequence of thetext in any of the claims does not imply that process steps must beperformed in a temporal or logical order according to such sequenceunless it is specifically defined by the language of the claim. Theprocess steps may be interchanged in any order without departing fromthe scope of the invention as long as such an interchange does notcontradict the claim language and is not logically nonsensical.

While at least one exemplary embodiment has been presented in theforegoing detailed description of the invention, it should beappreciated that a vast number of variations exist. It should also beappreciated that the exemplary embodiment or exemplary embodiments areonly examples, and are not intended to limit the scope, applicability,or configuration of the invention in any way. Rather, the foregoingdetailed description will provide those skilled in the art with aconvenient road map for implementing an exemplary embodiment of theinvention. It is understood that various changes may be made in thefunction and arrangement of elements described in an exemplaryembodiment without departing from the scope of the invention as setforth in the appended claims.

1. A method for orchestrating the re-configuration of a Time-TriggeredEthernet (TTE) network by providing scheduling and configurationinformation for a plurality of configuration definitions (CDs) within anetwork configuration superset (NCS) by a Network Scheduling Tool (NST),the method comprising: coupling a plurality of Feature Sets (FSs) to atleast one common control FS (CCFS) within the TTE network to enablecontrol by the NST of each FS by a runtime procedure wherein each FS ofthe plurality of FSs is composed of at least one group of Virtual Links(VLs); scheduling, by the NST, the plurality of features sets (FSs) ofthe TTE network based on at least one target configuration of aspecified FSs coupled to the CCFS within the TTE network; collecting, ina first scheduling pass by the NST, multiple FSs related to a pluralityof phase configurations wherein one or more of the FSs is used to derivea specified target FS configuration; and forming, by the NST, a commonFS by using an application to determine one or more features associatedwith each FS of the plurality of FSs.
 2. The method of claim 1, whereineach FS of the plurality of FSs comprises at least one VL specification,metadata set comprising identification information, and a miscellaneousdata set comprising inter-VL timing and protocol information for each VLspecification with a referenced FS.
 3. The method of claim 1, whereineach CD comprises at least one FS, metadata set comprisingidentification information, and a miscellaneous data set comprisingmodification information for each VL specification within a referencedFS.
 4. The method of claim 3, wherein the NCS comprises at least one CD,the metadata set comprising identification information, and themiscellaneous data set comprising network-wide static configurationparameters.
 5. The method of claim 4, further comprising: populating, bythe NST, a timeline divided into a generic global bin set designated asa baseline bin set for use in successive scheduling passes wherein theglobal bin set is preserved by the NST for further processing of theplurality of FSs and for populating of the timeline in successive passoperations.
 6. The method of claim 5, further comprising: reconfiguringincrementally, by the NST, as specified in at least one upgrade zone ofan individual plane of the TTE network wherein the NSCs transition fromoperating on a plane of a current CD to a newly specified CD associatedwith different FSs.
 7. The method of claim 6, further comprising:synchronizing, by the NST, by scheduling in a similar manner using theCCFS other FSs resulting in configured sets of VLs with a least amountof variations that compose the other FSs and preserving at least somecommonality between FSs in multiple target CDs in the NCS of the TTEnetwork.
 8. The method of claim 7, further comprising: re-configuring,by the runtime procedure, using specified upgrade zones composed ofselect NSC planes each new table associated with a corresponding CDuntil in incremental transitions a final CD configuration transition iscompleted.
 9. The method of claim 8, further comprising: scheduling, bythe NST, using the CCFS to preserve critical control of phases ofvehicle operation throughout each incremental transition wherein eachmutually exclusive FSs are scheduled on top of an existing scheduled FSsenabling VLs in each FS configuration to be configured in accordancewith one set of Network Interface Card (NIC) tables.
 10. The method ofclaim 9, further comprising: producing, by the NST, a unique NIC tablefor use by the NSC per target CD configuration.
 11. A system forimplementing a Network Scheduling Tool (NST) to schedule a plurality ofFeature Sets (FSs) comprising a plurality of Virtual Links (VLs) in aTime-Triggered Ethernet (TTE) network wherein each of the plurality ofVLs having a scheduled rate for a runtime procedure, the systemcomprising: a plurality of FSs comprising at least one ConfigurationDefinition (CD) in a Network Configured Superset (NCS) and, wherein theNST is configured to: schedule a plurality of features sets (FSs) of theTTE network based on at least one target CD of specified FSs within theTTE network; collect, in a first scheduling pass by the NST, multipleFSs related to a plurality of CDs wherein one or more of the FSs isreferenced by more than one CD; and form, a common control feature set(CCFS) by using an application to determine the FSs common to allspecified CDs in the NCS.
 12. The system of claim 11, wherein the NST isfurther configured to: populate a timeline associated with each FS witha generic global bin set designated as a baseline bin set for use insuccessive scheduling passes, wherein the global bin set is preserved bythe NST for further processing of the plurality of FSs and populate thetimeline in successive pass operations.
 13. The system of claim 12,wherein the NST is further configured to: re-configure incrementally asspecified in at least one upgrade zone of an individual plane of the TTEnetwork wherein the NSCs operate on that plane transition from a currentCD to a newly specified CD associated with a different FSs.
 14. Thesystem of claim 13, wherein the NST is further configured to: similarly,synchronize by scheduling using the CCFS other FSs that result inconfigured sets of VLs with a least amount of variations that compriseother FSs and preserve at least some degree of commonality between FSsin multiple target CDs in the NCS of the TTE network.
 15. The system ofclaim 14, wherein the NST is further configured to: re-configure usingspecified upgrade zones comprising select NSC planes each new tableassociated with a corresponding CD until in incremental transitions afinal CD configuration transition is completed.
 16. The system of claim15, wherein the NST is further configured to: schedule using the CCFS topreserve critical control of phases of vehicle operation throughout eachincremental transition wherein any mutually exclusive FSs can bescheduled on top of existing scheduled FSs enabling, VLs in each FSconfiguration to be configured in accordance with one set of NetworkInterface Card (NIC) tables.
 17. The system of claim 16, wherein the NSTis further configured to: produce a unique table for use by the NSC pertarget CD configuration.
 18. An apparatus configured with a NetworkScheduling Tool that comprises a processor to schedule a plurality ofconfiguration definitions (CDs) within a network configuration superset(NCS) in a Time-Triggered Ethernet (TTE) network, wherein the processoris programmed by a set of instructions to schedule time-triggeredtraffic, the processor configured to: schedule the VL specificationsdefined in a plurality of features sets (FSs) of the TTE network basedon at least one target CD of specified FSs within the TTE network;collect, in a first scheduling pass by the NST, multiple FSs related toa plurality of CDs wherein one or more of the FSs is referenced by morethan one CD; and form a common control feature set (CCFS) by using anapplication to determine the FSs common to all specified CDs in the NCS.19. The apparatus of claim 18, wherein the processor is furtherprogrammed to: populate a timeline associated with each FS and VLspecification using a generic global bin set designated as a baselinebin set for use in successive scheduling passes, wherein the global binset is preserved by the NST for further processing of the plurality ofFSs and populating of the timeline in successive pass operations. 20.The apparatus of claim 19, wherein the processor is further programmedto: re-configure incrementally using specified upgrade zones composed ofselect NSC planes each new table associated with a corresponding CDuntil in incremental transitions a final CD configuration transition iscompleted; and similarly synchronize by scheduling using the CCFS, otherFSs resulting in configured sets of VLs with a least amount ofvariations that compose the other FSs, and preserve at least somecommonality between FSs in multiple target CDs in the NCS of the TTEnetwork.